I was brought in to fix broken marketing operations where content requests took too long and delivery timelines were unpredictable.
Marketing teams used internal tools to request content, but briefing templates were blank text boxes. This meant endless clarification emails, missed deadlines, expensive rework, and frustrated stakeholders.
Over seven months, I redesigned briefing templates, managed the product backlog, and delivered features that made the system work.
Templates were unstructured text fields requiring multiple clarification cycles before production could begin.
Without standardised processes, delivery timelines varied. Teams couldn't plan effectively or schedule campaigns reliably.
Ambiguous briefs led to assumptions. When incorrect, content required extensive revisions, increasing costs.
Tools evolved organically without product strategy. Different markets used different workflows.
Once requests entered the system, stakeholders had minimal progress insight. Managers received constant status inquiries.
Each market developed unique workarounds. Fragmentation made it difficult to implement improvements at scale.
After conducting 30+ stakeholder interviews, the fundamental issue became clear: this was a systems problem, not a people problem. Teams were working diligently within broken processes. Templates didn't capture essential information. Tools lacked basic functionality. Processes had never been intentionally designed.
Conducted 30+ interviews with marketing teams, production managers, agency partners, and approval stakeholders.
Documented complete journey from request submission through delivery. Identified all handoffs and failure points.
Analysed historical data to quantify cycle times and identify bottlenecks. Clarification cycles consumed 40% of request time.
| Issue | Impact | Root Cause |
|---|---|---|
| Incomplete Briefs | 35% required 2+ clarification rounds | Templates lacked structured fields |
| Unclear Approvals | 3 days lost per approval stage | Approval workflows undefined |
| Missing Specifications | 40% of assets required rework | No technical specification requirements |
| Status Requests | 100+ status emails weekly | No real-time tracking capability |
| Manual Routing | Requests frequently misdirected | No automated routing logic |
Developed 6-month roadmap balancing immediate improvements with strategic capabilities.
Maintained prioritised backlog using impact divided by effort to optimise resources.
Implemented 2-week sprint cycles with proper scoping, testing, and communication.
Established feedback mechanisms to inform ongoing development priorities.
Stakeholder research, process mapping, data analysis, bottleneck identification, business case development
Template design workshops, field validation, quick-win feature delivery (status visibility, notifications, reporting)
Strategic features (routing, workflows, SLA tracking), pilot programme, regional expansion, global deployment
| Feature | Priority | Status | Impact |
|---|---|---|---|
| MUST HAVE | |||
| Template Library | P0 | ✅ Delivered | Critical |
| Auto-routing | P0 | ✅ Delivered | Critical |
| Status Dashboard | P0 | ✅ Delivered | High |
| Approval Workflows | P1 | ✅ Delivered | High |
| Feature | Priority | Status | Impact |
|---|---|---|---|
| SHOULD HAVE | |||
| SLA Tracking | P1 | ✅ Delivered | High |
| Duplicate Detection | P1 | ✅ Delivered | Medium |
| Analytics Platform | P1 | ✅ Delivered | High |
| Escalation Logic | P2 | ✅ Delivered | Medium |
Prioritisation: Impact score divided by effort score. Features scoring above 2.0 were prioritised for development.
The 20% reduction in cycle time represents approximately 3 days saved per request. With over 200 monthly requests, this translates to roughly 600 days of annual capacity returned.
The 40% reduction in rework resulted in approximately 30% fewer agency hours required per request, delivering tangible cost savings.
The 75% decrease in status inquiry emails freed production managers to focus on value-adding activities.
Marketing Manager, Germany
"Having visibility into request status has fundamentally changed how I plan campaign timelines."Creative Director, UK
Comprehensive process mapping revealed bottlenecks that weren't apparent when examining individual touchpoints. The most significant issues occurred at handoff points between teams.
Effective briefing templates serve dual purposes: guiding requesters through strategic thinking while capturing operational requirements.
Applying product management disciplines to internal tools transforms their effectiveness. This shifts focus from reactive maintenance to strategic capability development.
While markets initially resisted standardisation, consistent processes ultimately facilitated easier customisation. Standardisation provides the foundation for sustainable local adaptation.
Technical implementation represents approximately 50% of programme effort. Training, communication, and transition support require equal investment to ensure adoption.
Process improvement succeeds when addressing both system design and user adoption simultaneously. Optimal templates fail without user engagement. Enthusiastic users cannot succeed with inadequate tools.